SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Problem statement</title>

</head>

Problem statement

</h1>

</header>

A problem statement is a description of an issue to be addressed, or a condition to be improved upon. It identifies the gap between the current problem and goal. The first condition of solving a problem is understanding the problem, which can be done by way of a problem statement.<a href="#cite_note-:0-1">[1]</a>

Problem statements are used by most businesses and organizations to execute process improvement projects.<a href="#cite_note-:1-2">[2]</a>

<div class="mw-heading mw-heading2"><h2 id="Purpose">Purpose</h2></div>

The main purpose of a problem statement is to identify and explain the problem.<a href="#cite_note-:2-3">[3]</a><a href="#cite_note-:3-4">[4]</a>

Another function of the problem statement is as a communication device.<a href="#cite_note-:2-3">[3]</a> Before the project begins, <a href="Stakeholder_(corporate)" title="Stakeholder (corporate)">stakeholders</a> verify the problem and goals are accurately described in the problem statement. Once approved, the project reviews it. This also helps define <a href="Scope_(project_management)" title="Scope (project management)">project scope</a>.<a href="#cite_note-:4-5">[5]</a>

The problem statement is referenced throughout the project to establish focus within the project team and verify they stay on track. At the end of the project, it is revisited to confirm the solution indeed solves the problem.

The problem statement does not define the solution or methods of reaching the solution, and only recognizes the gap between the problem and goal.<a href="#cite_note-:3-4">[4]</a><a href="#cite_note-:5-6">[6]</a>

<div class="mw-heading mw-heading2"><h2 id="Writing">Writing</h2></div>

There are several basic elements that can be built into every problem statement. The problem statement should focus on the <a href="End_user" title="End user">end user</a>, and the statement should not be too broad or narrow.<a href="#cite_note-:7-7">[7]</a>

Problem statements usually follow a format. While there are several options, the following is a template often used in <a href="Business_analysis" title="Business analysis">business analysis</a>.

<ol><li>Ideal: The desired state of the process or product.</li>

<li>Reality: The current state of the process or product.</li>

<li>Consequences: The impacts on the business if the problem is not fixed or improved upon.</li>

<li>Proposal: Potential solutions.<a href="#cite_note-:6-8">[8]</a></li></ol>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite id="CITEREFKush2015" class="citation journal cs1">Kush, Max (June 2015). "The Statement Problem". Quality Progress. 48 (6).</cite>

</li>

<li id="cite_note-:1-2"><a href="#cite_ref-:1_2-0">^</a> <cite id="CITEREFAnnamalaiKamaruddinAzidYeoh2013" class="citation journal cs1">Annamalai, Nagappan; Kamaruddin, Shahrul; Azid, Ishak Abdul; Yeoh, TS (September 2013). "Importance of Problem Statement in Solving Industry Problems". Applied Mechanics and Materials. 421. Zurich: 857–863. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.4028%2Fwww.scientific.net%2FAMM.421.857">10.4028/www.scientific.net/AMM.421.857</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:60791623">60791623</a>.</cite>

</li>

<li id="cite_note-:2-3">^ <a href="#cite_ref-:2_3-0">a</a> <a href="#cite_ref-:2_3-1">b</a> <cite id="CITEREFGygiDeCarloWilliams2015" class="citation book cs1">Gygi, Craig; DeCarlo, Neil; Williams, Bruce (2015). Six sigma for dummies. Hoboken, NJ: John Wiley & Sons. pp. 76–78.</cite>

</li>

<li id="cite_note-:3-4">^ <a href="#cite_ref-:3_4-0">a</a> <a href="#cite_ref-:3_4-1">b</a> <cite id="CITEREFLindstrom2011" class="citation web cs1">Lindstrom, Chris (2011-04-24). <a rel="nofollow" class="external text" href="http://www.ceptara.com/blog/how-to-write-problem-statement">"How To Write A Problem Statement"</a>. www.ceptara.com. Retrieved 2018-04-10.</cite>

</li>

<li id="cite_note-:4-5"><a href="#cite_ref-:4_5-0">^</a> <cite id="CITEREFPerryBacon2010" class="citation book cs1">Perry, Randy; Bacon, David (2010). Commercializing Great Products with Design for <a href="Six_Sigma" title="Six Sigma">Six Sigma</a>. Prentice Hall. p. 18.</cite>

</li>

<li id="cite_note-:5-6"><a href="#cite_ref-:5_6-0">^</a> <cite id="CITEREFShaffer2017" class="citation news cs1">Shaffer, Deb (2017-07-12). <a rel="nofollow" class="external text" href="https://www.proprojectmanager.com/problem-statement/">"How to Write a Problem Statement"</a>. ProProject Manager. Retrieved 2018-04-10.</cite>

</li>

<li id="cite_note-:7-7"><a href="#cite_ref-:7_7-0">^</a> <cite id="CITEREFWiden2018" class="citation news cs1">Widen, Steven (2018-04-02). <a rel="nofollow" class="external text" href="https://www.forbes.com/sites/forbesagencycouncil/2018/04/02/take-these-steps-to-define-your-uiux-problem-and-avoid-haphazard-changes/#22f21cda7c6c">"Take These Steps To Define Your UI/UX Problem And Avoid Haphazard Changes"</a>. Forbes. Retrieved 2018-04-10.</cite>

</li>

<li id="cite_note-:6-8"><a href="#cite_ref-:6_8-0">^</a> <cite id="CITEREFShaffer2015" class="citation web cs1">Shaffer, David (2015-12-21). <a rel="nofollow" class="external text" href="https://www.batimes.com/articles/cooking-up-business-analysis-success.html">"Cooking Up Business Analysis Success"</a>. BA Times. Retrieved 2018-04-10.</cite>

</li>

</ol></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2024-09-15" href="https://en.wikipedia.org/wiki/?title=Problem_statement&oldid=1245832216">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>